You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
If we use namenode.getBlockLocations() , the blockToken AccessMode is BlockTokenIdentifier.AccessMode.READ. I also test in a real hdfs cluster with FastCopy.
Hello ,sirs . For some reason, I now work with fastcopy and current progerss is that I now already finished fastcopy tools in standalone mode. Both replicated files and EC files are supported. And next is trying to finish distcp with fastcopy. @haiyang1987 , are you still work on this ? If not ,I hope to finish the rest of the work. Thanks you.
And @ZanderXu@ayushtkn@Hexiaoqiao Sirs, can we continue to push this mission forward? FastCopy is more efficient
for data replication in a single hdfs cluster or a federation hdfs cluter with more nameservices. Thanks!
The reason will be displayed to describe this comment to others. Learn more.
If srcBlock targetBlock not in a same datanode, it will use DataTransfer . And DataTransfer will catch any exception in thread , so result.get() will always can not catch IOException.
Hello ,sirs . For some reason, I now work with fastcopy and current progerss is that I now already finished fastcopy tools in standalone mode. Both replicated files and EC files are supported. And next is trying to finish distcp with fastcopy. @haiyang1987 , are you still work on this ? If not ,I hope to finish the rest of the work. Thanks you. And @ZanderXu@ayushtkn@Hexiaoqiao Sirs, can we continue to push this mission forward? FastCopy is more efficient for data replication in a single hdfs cluster or a federation hdfs cluter with more nameservices. Thanks!
Thanks @LiuGuH for your comment. I will check it based on your suggestion later.
Of course, you can finish to work other subtasks. Fast Copy is really a good feature, hope we continue to push this. thanks!
We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
Thanks all for your contribution.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description of PR
As described in https://issues.apache.org/jira/browse/HDFS-16757 :
Add a new method copyBlockCrossNamespace to Datanode to support fast copy.